Studying re-opened bugs in open source software
نویسندگان
چکیده
منابع مشابه
Bug Fixes vs . Re - opened Bugs
A typical bug fixing cycle involves the reporting of a bug, the triaging of the report, the production and verification of a fix, and the closing of the bug. However, previous work has studied two phenomena where more than one fix are associated with the same bug report. The first one is the case where developers re-open a previously fixed bug in the bug repository (sometimes even multiple time...
متن کاملOpen-source software for studying neural codes
In this chapter we first outline some of the popular computing environments used for analysing neural data, followed by a brief discussion of 'software carpentry', basic tools and skills from software engineering that can be of great use to computational scientists. We then introduce the concept of open-source software and explain some of its potential benefits for the academic community before...
متن کاملUsability bugs in open-source software and online forums
The unlimited number of open-source software (OSS) users and the importance of end users’ experience in determining software quality make usability an even more critical quality attribute for OSS than it is for proprietary software. The research model of this study establishes the relationship between usability errors in OSS and online public forums. The results of this empirical analysis provi...
متن کاملA Study of Concurrency Bugs in an Open Source Software
Concurrent programming puts demands on software debugging and testing, as concurrent software may exhibit problems not present in sequential software, e.g., deadlocks and race conditions. In aiming to increase efficiency and effectiveness of debugging and bug-fixing for concurrent software, a deep understanding of concurrency bugs, their frequency and fixing-times would be helpful. Similarly, t...
متن کاملEyeballs, Bugs, and Releases in Open Source Software
This study examines two widely cited principles of Linus’ law, namely “given enough eyeballs, all bugs are shallow”, and “release early and release often”. The aim is to understand their relationships and their limits to debugging open source software (OSS) bugs. Anecdotally, most of the successful OSS groups seldom develop in isolation; and their bugs and the underlying debugging processes are...
متن کاملذخیره در منابع من
با ذخیره ی این منبع در منابع من، دسترسی به آن را برای استفاده های بعدی آسان تر کنید
ژورنال
عنوان ژورنال: Empirical Software Engineering
سال: 2012
ISSN: 1382-3256,1573-7616
DOI: 10.1007/s10664-012-9228-6